Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@src/components/mui/formik-inputs/mui-formik-async-select.js`:
- Around line 34-35: The component defines and accepts isMulti but still uses
the older multiple flag when computing Autocomplete value and onChange, causing
Formik to store the wrong shape; update all selection/value logic to
consistently use isMulti (not multiple) — pass isMulti to the MUI Autocomplete
prop, branch on isMulti when deriving value from Formik field and when calling
setFieldValue (map arrays for multi-select, single item otherwise), and
remove/rename any references to multiple so Formik and Autocomplete agree on the
value shape (check functions/variables around isMulti, Autocomplete usage, and
the onChange/value handlers).
- Around line 107-110: The local filtering callback currently calls
opt.label.toLowerCase() which will throw if opt.label is
null/undefined/non-string; update the filter used in options.filter((opt) =>
...) to coerce or guard the label and inputValue (e.g., use String(opt.label ??
'') or (opt.label || '').toString()) and similarly normalize inputValue before
calling toLowerCase(), then perform the includes check; ensure you update the
inline filter expression where options.filter is defined to be null-safe for
labels.

In `@src/components/mui/formik-inputs/mui-formik-color-input.js`:
- Line 8: The localValue state initialized with useState(field.value ||
"#000000") can become stale on form resets; add an effect that listens for
changes to field.value (the Formik value) and calls setLocalValue(field.value ??
"#000000") to keep the color swatch in sync; locate the localValue and
setLocalValue declarations in mui-formik-color-input.js and add a useEffect
referencing field.value to update localValue when Formik reinitializes or
resets.
- Around line 20-34: The TextField currently spreads {...rest} last which allows
callers to override controlled props (type, value, onChange, onBlur) and bypass
Formik; update the component that renders TextField so you either spread
{...rest} first (before value={localValue}, onChange={handleChange},
onBlur={handleBlur}, type="color") or, preferably, strip conflicting keys from
rest (delete or omit 'type','value','onChange','onBlur') before spreading into
TextField; ensure the retained props are localValue, handleChange, handleBlur,
and the type remains "color" so Formik binding (meta.touched/meta.error) cannot
be overridden.

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Duplicate comments:
In `@src/components/mui/formik-inputs/mui-formik-async-select.js`:
- Around line 115-118: The filterOptions callback in mui-formik-async-select.js
can throw when an option has a null/undefined label; update the filter function
used by filterOptions (the arrow function in that file) to defensively coerce
the label to a string before calling toLowerCase (e.g., use (opt && (opt.label
?? '')) or String(opt?.label ?? '') then toLowerCase) and also guard against opt
being falsy, so options with missing labels no longer crash the filtering logic.
- Around line 42-43: The component mixes two names for the same concept: use the
single prop name isMulti everywhere to avoid shape mismatches. Update the
handleChange function to branch on isMulti (not multiple), ensure the
Autocomplete is passed multiple={isMulti}, and remove/normalize any use of a
separate multiple prop in the component props/destructuring so Formik always
receives the value shape that matches Autocomplete's multiple={isMulti}
behavior.

---

Nitpick comments:
In `@src/components/mui/formik-inputs/mui-formik-async-select.js`:
- Around line 158-164: The propTypes for MuiFormikAsyncAutocomplete are missing
six props (multiple, placeholder, plainValue, hiddenOptions,
formatSelectedValue, isMulti); update the MuiFormikAsyncAutocomplete.propTypes
object to include these properties with appropriate types (multiple:
PropTypes.bool, isMulti: PropTypes.bool, placeholder: PropTypes.string,
plainValue: PropTypes.bool, hiddenOptions: PropTypes.array, formatSelectedValue:
PropTypes.func) so React dev-mode warnings catch misuse, and ensure the
component’s defaultProps (if any) and internal logic treat isMulti and multiple
consistently.

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@src/components/mui/formik-inputs/mui-formik-color-input.js`:
- Around line 16-19: The cleanup in the useEffect currently writes to Formik
(reads field.value and calls helpers.setValue("#000000")) using a stale closure;
remove the conditional Formik write from the cleanup so it no longer mutates
Formik state on unmount—keep only the debounce timeout cleanup
(clearTimeout(debounceRef.current)) in the useEffect cleanup. Locate the
useEffect that references field.value, helpers.setValue, and debounceRef and
delete the helpers.setValue branch, leaving the debounceRef.current clear call
intact (handleBlur already flushes debounced updates).

---

Outside diff comments:
In `@src/components/mui/formik-inputs/mui-formik-async-select.js`:
- Around line 68-75: The effect only calls fetchOptions when searchTerm is
truthy, leaving stale remote results when the input is cleared; update the
useEffect that references localFilter, searchTerm, fetchOptions and
DEBOUNCE_WAIT_250 so that when localFilter is falsy and searchTerm is falsy it
triggers a refresh for the empty/default query (e.g., call fetchOptions('') or
fetchOptions(undefined)) instead of doing nothing; keep the debounce behavior
for non-empty searchTerm but invoke the empty-query refresh immediately (or with
its own short debounce) and ensure the clearTimeout cleanup remains in place.

---

Duplicate comments:
In `@src/components/mui/formik-inputs/mui-formik-color-input.js`:
- Around line 42-57: The TextField spreads {...rest} last which allows callers
to override Formik-controlled props (value, onChange, onBlur, name, type);
change the render so controlled props from Formik take precedence by moving
{...rest} before the explicit props or by explicitly picking allowed passthrough
props and spreading only those (update the JSX using TextField, localValue,
handleChange, handleBlur, meta, and field to ensure value={localValue},
onChange={handleChange}, onBlur={handleBlur}, name={field.name}, and
type="color" cannot be overridden).